Skip to content

Add disableJsonB option to NOT use avaje-jsonb in code generation eve…#574

Merged
rbygrave merged 1 commit into
masterfrom
feature/add-disableJsonB-option
Mar 10, 2025
Merged

Add disableJsonB option to NOT use avaje-jsonb in code generation eve…#574
rbygrave merged 1 commit into
masterfrom
feature/add-disableJsonB-option

Conversation

@rbygrave
Copy link
Copy Markdown
Contributor

…n if it's in the classpath

@rbygrave rbygrave self-assigned this Mar 10, 2025
Copy link
Copy Markdown
Collaborator

@SentryMan SentryMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but what brought this on?

@rbygrave
Copy link
Copy Markdown
Contributor Author

Had someone creating a Nima rest api, it was using JAX-B generated classes for request/response types ... and those used java.util.Calendar [and also no setters for the collections]. So there wasn't a relatively quick/easy way to turn off the use of avaje-jsonb in the generated code and just use Jackson [apart from removing avaje-jsonb entirely from the classpath].

So this is there to support that type of case, where someone hits some issue and just wants to "downgrade" to using Jackson [perhaps temporarily until any issue with avaje-jsonb is sorted].

@rbygrave rbygrave merged commit 70d908c into master Mar 10, 2025
@rbygrave rbygrave deleted the feature/add-disableJsonB-option branch March 10, 2025 03:46
@SentryMan SentryMan added this to the 3.1 milestone Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants